Managing non?functional requirements in agile software development

Non-functional requirements define qualities of the software system that ensure effectiveness while embedding any constraints and restrictions on design. A challenge rises with agile implementation in handling non-function regulated environments. Thus, a practitioner's perceptions method tailoring are described relation to inter-team boundaries non-functional requirements. The research comprises 18 practitioner interviews from two multinational development companies. Interviews were recorded, transcribed, analysed using an approach informed by grounded theory information flow models used compare contrast interactions processes. It was discovered one case study companies managed as artefacts their methodology, other company reverts conventional plan-based practices documentation, timeline estimations, safety critical This creates detailed comparison these contrasting approaches. main contribution this is set proposed recommendations deal environment techniques. introduction new artefacts, Documentation Work Item Safety Critical Item, recommended it accompanied illustrative example, transform documentation more way.